StackBlitz Support for the Quickstart Samples - #47
Conversation
feat: add .stackblitzrc for Vue quickstart sample docs: add StackBlitz badge to Vue quickstart README fix: update hrefs in Vue HomePage component for flows and design guides chore: remove unused .env.example and README from Next.js template chore: remove unused files from Next.js template chore: remove unused files from Nuxt template chore: remove unused files from React Vite template chore: remove unused files from Vue Vite template
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (52)
💤 Files with no reviewable changes (33)
📝 WalkthroughWalkthroughThe PR adds StackBlitz support and launch badges to eight quickstart samples, fixes duplicated documentation URL segments, removes the starter templates, and removes ChangesQuickstart StackBlitz support
Template removal and repository cleanup
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related issues
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Purpose
The seven quickstart samples under
samples/(react, vue, browser, express, node, nextjs, nuxt) couldn't be opened via a StackBlitz GitHub-fork link. Each sample declares its ThunderID SDK dependency asworkspace:*for local pnpm-workspacedevelopment, but StackBlitz forks only the singleh no visibility into the rest of the monorepo, so
workspace:*can never resolve and the install fails immediately.This PR adds StackBlitz support to all seven quickstarts and adds an "Open in StackBlitz" badge to each sample's README.
Approach
.stackblitzrcto eachsamples/<sdk>/quickstart/withinstallDependencies: falseand astartCommandthat:node -eone-liner that rewrites anyworkspace:*entries independencies/devDependenciestolatest, so the sample resolves against the real published packages instead of the (unavailable) sibling workspace packages.npm install && npm run dev.npminstead ofpnpmfor the StackBlitzult supported by StackBlitz's Node WebContainerwithout extra corepack setup, and matches how the previous stray lockfile issue below was resolved..stackblitzrcrather than shipping a separate script file per sample — since each StackBlitz fork only pulls in the single quickstart subfolder (not the rest of the repo), any fixup logic has to beself-contained in that folder anyway, and inlininkeep in sync across all seven samples.
samples/react/quickstart/pnpm-lock.yaml, which had been mistakenly committed for that one sample (the other six correctly rely on the root workspace lockfile only, since this is a pnpm workspace).package.jsonfiles,pnpm-workspace.yaml, and the pnpmcatalog:setup are untouched —workspace:*stillresolves correctly for local monorepo development transiently inside the StackBlitz container.
@thunderid/react/@thunderid/react-routermatch what's in the workspace, so resolving tolatestis safe today.Related Issues
Related PRs
Checklist
breaking changelabel added.Security checks
Summary by CodeRabbit
New Features
Bug Fixes
Chores